Unit of Competency Mapping – Information for Teachers/Assessors – Information for Learners

ICTPRG520 Mapping and Delivery Guide
Validate an application design against specifications

Version 1.0
Issue Date: May 2024


Qualification -
Unit of Competency ICTPRG520 - Validate an application design against specifications
Description
Employability Skills
Learning Outcomes and Application This unit describes the skills and knowledge required to check a software application design against the specifications, and to apply validation techniques across the system’s life cycle.It applies to individuals employed in the area of software development who are responsible for verifying and validating software design specifications. They may be software project managers, testers, software engineers, system analysts or software developers.No licensing, legislative or certification requirements apply to this unit at the time of publication.
Duration and Setting X weeks, nominally xx hours, delivered in a classroom/online/blended learning setting.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

tools to create prototype systems

static analysis tools

test plan and test cases.

Assessors must satisfy NVR/AQTF assessor requirements.
Prerequisites/co-requisites
Competency Field
Development and validation strategy and guide for assessors and learners Student Learning Resources Handouts
Activities 		Slides
PPT 		Assessment 1 Assessment 2 Assessment 3 Assessment 4
Elements of Competency Performance Criteria              
Element: Evaluate the software requirement specifications
  • Review the software requirement specifications document prior to design, to ensure that it is complete and correct
  • Validate the software requirement specifications document
       
Element: Create a proof of concept prototype
  • Use rapid application development tools (RAD) to create a prototype system
  • Present the prototype system for demonstration to the appropriate person
  • Validate the proof of concept
       
Element: Evaluate the software design
  • Determine if the design is complete, accurate, consistent and feasible
  • Validate the software design document
  • Validate the database structure and its elements
  • Validate the user interface (UI)
  • Review the software risk analysis
       
Element: Evaluate the source code
  • Validate the consistency between the code and the software design document
  • Validate logical structure and syntax, using static analysis tools
       
Element: Evaluate the testing requirements
  • Review and validate the test plans
  • Review and validate the test cases
       
Element: Document the validation
  • Document the results of the validation exercise
  • Recommend the current software design, or itemise the required alterations
  • Submit the report to the appropriate person for action
       


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Evaluate the software requirement specifications

1.1 Review the software requirement specifications document prior to design, to ensure that it is complete and correct

1.2 Validate the software requirement specifications document

2. Create a proof of concept prototype

2.1 Use rapid application development tools (RAD) to create a prototype system

2.2 Present the prototype system for demonstration to the appropriate person

2.3 Validate the proof of concept

3. Evaluate the software design

3.1 Determine if the design is complete, accurate, consistent and feasible

3.2 Validate the software design document

3.3 Validate the database structure and its elements

3.4 Validate the user interface (UI)

3.5 Review the software risk analysis

4. Evaluate the source code

4.1 Validate the consistency between the code and the software design document

4.2 Validate logical structure and syntax, using static analysis tools

5. Evaluate the testing requirements

5.1 Review and validate the test plans

5.2 Review and validate the test cases

6. Document the validation

6.1 Document the results of the validation exercise

6.2 Recommend the current software design, or itemise the required alterations

6.3 Submit the report to the appropriate person for action

Evidence of the ability to:

interpret and check software requirement specifications documents

use rapid application development (RAD) tools to create and present a validated proof of concept prototype

validate the software design, source code and testing requirements and document the results

report on results of validation, including recommended actions.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

explain the database design and implementation

describe business and technical modelling using UML tools at intermediate level

outline current software development methodologies

describe, in detail, the system development life cycle (SDLC)

explain object-oriented programming

describe open-source development tools

describe software-testing techniques.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assignment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Evaluate the software requirement specifications

1.1 Review the software requirement specifications document prior to design, to ensure that it is complete and correct

1.2 Validate the software requirement specifications document

2. Create a proof of concept prototype

2.1 Use rapid application development tools (RAD) to create a prototype system

2.2 Present the prototype system for demonstration to the appropriate person

2.3 Validate the proof of concept

3. Evaluate the software design

3.1 Determine if the design is complete, accurate, consistent and feasible

3.2 Validate the software design document

3.3 Validate the database structure and its elements

3.4 Validate the user interface (UI)

3.5 Review the software risk analysis

4. Evaluate the source code

4.1 Validate the consistency between the code and the software design document

4.2 Validate logical structure and syntax, using static analysis tools

5. Evaluate the testing requirements

5.1 Review and validate the test plans

5.2 Review and validate the test cases

6. Document the validation

6.1 Document the results of the validation exercise

6.2 Recommend the current software design, or itemise the required alterations

6.3 Submit the report to the appropriate person for action

Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Review the software requirement specifications document prior to design, to ensure that it is complete and correct 
Validate the software requirement specifications document 
Use rapid application development tools (RAD) to create a prototype system 
Present the prototype system for demonstration to the appropriate person 
Validate the proof of concept 
Determine if the design is complete, accurate, consistent and feasible 
Validate the software design document 
Validate the database structure and its elements 
Validate the user interface (UI) 
Review the software risk analysis 
Validate the consistency between the code and the software design document 
Validate logical structure and syntax, using static analysis tools 
Review and validate the test plans 
Review and validate the test cases 
Document the results of the validation exercise 
Recommend the current software design, or itemise the required alterations 
Submit the report to the appropriate person for action 

Forms

Assessment Cover Sheet

ICTPRG520 - Validate an application design against specifications
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG520 - Validate an application design against specifications

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: